Managing instant messaging sessions on multiple devices

ABSTRACT

Transferring instant messaging sessions includes receiving a selection, from a user within a user interface, of at least one instant messaging session from among multiple instant messaging sessions to transfer from a first instant messaging controller on a first device to at 5 least a second instant messaging controller on a second device, where the user is signed on concurrently to the first instant messaging controller on the first device and the second instant messaging controller on the second device. At least a portion of the selected instant messaging session is transferred from the first instant messaging controller on the first device to the second instant messaging controller on the second device and the transferred portion of 10 the instant messaging session is made perceivable on the second instant messaging controller on the second device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of priorityto U.S. application Ser. No. 13/010,046 filed Jan. 20, 2011 (nowallowed). U.S. application Ser. No. 13/010,046 is a continuation of U.S.application Ser. No. 12/022,437 filed Jan. 30, 2008 (now U.S. Pat. No.7,877,450). U.S. application Ser. No. 12/022,437 is a continuation ofU.S. application Ser. No. 11/025,849, filed Dec. 30, 2004 (now U.S. Pat.No. 7,356,567). Each of the above-referenced applications isincorporated by reference to its entirety.

TECHNICAL FIELD

This document relates to managing instant messaging sessions on multipledevices.

BACKGROUND

Instant messaging is one manner in which online identities maycommunicate with each other electronically. A user may be able access aninstant messaging online identity multiple times from multiple differentdevices. For example, the user may log into the user's instant messagingonline identity through an instant messaging application on the user'sdesktop personal computer at home. At the same time, the user may loginto the same instant messaging online identity through an instantmessaging application on the user's personal digital assistant.

Unlike email that is persistent, instant messaging is intended to enableongoing and continuous, though segmented, dialog between two userssubstantially in real time. As such, an instant messaging user interfaceappears on a device use to inspire or receive an instant message,reflecting content presently sent or received by the instant messagingparticipants.

If two or more instant messaging controllers concurrently are run by asingle online identity, an instant messaging user interface will appearon both controllers each time an instant message is received by thatidentity, whether or not the identity is actively operating devices atwhich those controllers are run.

Moreover, when a user inspires a message, their message appears only onthe instant messaging user interface of the device from which themessage was inspired. For example, if a user concurrently runs aninstant messaging controller on a desktop and a personal digitalassistant (PDA), and the user inspires a message using the instantmessaging controller on the desktop, the instant messaging userinterface does not appear on the PDA to reflect the instant message sentby the user from the desktop.

When a reply to the user's instant message is received, and it inspiresan instant messaging user interface on both devices, the PDA interfaceremains without an indication of the message that the user sent toinspire the reply.

DESCRIPTION OF DRAWINGS

FIG. 1 is a flow chart of an exemplary process for enabling a user totransfer an instant messaging session.

FIG. 2 is an exemplary screen shot of a participant list.

FIGS. 3A-3C are exemplary screen shots illustrating an instant messagingsession transfer interface.

FIGS. 4A and 4B are exemplary screen shots illustrating aspects of aninstant messaging conversation interface.

FIGS. 5A and 5B are exemplary interfaces of instant messaging sessionmirror request interfaces.

FIG. 6A illustrates an exemplary timeline.

FIG. 6B illustrates an exemplary selection interface.

FIG. 7 is a block diagram of a communications system.

FIG. 8 is an expansion of the block diagram of FIG. 7.

Like reference symbols in the various drawings may indicate likeelements.

DETAILED DESCRIPTION

In a world of ubiquitous device usage and portability, it becomesimportant to intelligently manage instant messaging conversation contentpresented at devices concurrently logged into an instant messagingservice. One aspect of intelligent management involves replicating ortransitioning information related to ongoing instant messagingconversations from an incumbent instant messaging controller to anotherinstant messaging controller that has newly been run, automatically orin response to user input. Another aspect involves managing presentationof information and multiple concurrently running instant messagingcontrollers in an ongoing basis.

More specifically, convenient access to the content (and/orbibliographic information) for current instant messaging conversationsacross multiple instant messaging controllers on different devices maybe provided in several ways. In one exemplary implementation, a user isallowed to transfer (e.g., copy or transition) one or more currentinstant messaging sessions from among multiple instant messagingsessions from an instant messaging controller on one device to aninstant messaging controller on another device. For instance, a user maysign on to an instant messaging system using an online identity (e.g.,screen name) on an instant messaging controller on a desktop computer.The user may have multiple instant messaging sessions with multipledifferent co-users. If the user needs to leave the desktop computer anddesires to continue a subset of those multiple instant messagingsessions, then the user may log on to an instant messaging controller onanother device, such as a personal digital assistant (PDA), and transfera subset of the multiple instant messaging sessions to the PDA. The fulltext of the transferred instant messaging sessions are made perceivableon the PDA, thus, enabling the user to seamlessly continue the existinginstant messaging conversations by referencing some or all of the textof the conversation communicated prior to their logging onto the instantmessaging controller on the PDA.

In one exemplary implementation, the user may initiate the transfer ofall or a subset of the ongoing instant messaging session from either theinstant messaging controller on the incumbent device or the instantmessaging controller on the later-invoked device. Thus, in the examplediscussed above, the user may initiate the transfer of the instantmessaging sessions from either the instant messaging controller on thedesktop computer or the instant messaging controller on the PDA.

Different user interfaces may be used to transfer the instant messagingsessions. In one exemplary implementation, an instant messaging sessiontransfer interface may be used to transfer one or more instant messagingsessions from among multiple instant messaging sessions. The instantmessaging session transfer interface may be accessed and used fromeither the instant messaging controller on the incumbent device or theinstant messaging controller on the later-invoked device. In anotherexemplary implementation, an instant messaging conversation interfacemay be configured to enable transfer of a corresponding instantmessaging session.

In addition to selecting the particular instant messaging sessions totransfer, the user also may select the device to receive or send theinstant messaging sessions. For example, if the user is signed on tothree instant messaging controllers on three different devices, then theuser may select which of two devices to send one or more (or all)instant messaging sessions. Additionally and/or alternatively, the usermay select which of two devices from which to receive one or more (orall) instant messaging sessions.

When an instant messaging session is perceivable on more than oneinstant messaging controller, the exchange of instant messages betweenthe user and the co-user in instant messaging session may be mirrored onall or less than all of the instant messaging controllers. The user maydesignate preferences as to whether the instant messaging sessionsshould be mirrored prior to and/or after the transfer.

In one exemplary implementation, an idle or an away state of the instantmessaging controller may disrupt the viewing of a mirrored instantmessaging session. When the user returns to a device where the displayof the instant messaging session was interrupted due to an idle or anaway state, the interrupted instant messaging session may be refreshed.In one implementation, the display of the interrupted instant messagingsession may be refreshed automatically upon the instant messagingcontroller transitioning into an active state. In another exemplaryimplementation, an interface may be used to designate which of the oneor more interrupted instant messaging sessions to refresh.

In yet another exemplary implementation, when an instant messagingsession is transferred back to a device, the legacy instant messagingconversation interface may be refreshed with the entire instantmessaging session or the legacy instant messaging conversation interfacemay be closed and a new instant messaging conversation interfaceinstantiated and populated with the entire instant messagingconversation.

FIG. 1 illustrates an exemplary process 100 for transferring an instantmessaging session. A selection is received identifying at least oneinstant messaging session from among multiple instant messaging sessionsto be transferred from a first instant messaging controller on a firstdevice to at least a second instant messaging controller on a seconddevice, where the user is signed on concurrently to at least the firstinstant messaging controller on the first device and the second instantmessaging controller on the second device (step 105). The selectedinstant messaging session is transferred from the first instantmessaging controller on the first device to the second instant messagingcontroller on the second device (step 115) and the transferred instantmessaging session is made perceivable on the second instant messagingcontroller on the second device (step 120).

An instant messaging session is a communication session that isestablished between a user and at least one co-user, where the user andthe co-user can exchange instant messages in an instant messagingconversation interface. A user may have multiple instant messagingsession ongoing at the same time with many different co-users, with eachseparate instant messaging conversation being made perceivable to theuser in a corresponding instant messaging conversation interface.

An instant messaging session may be established using an instantmessaging controller and a device. An example of a device is ageneral-purpose computer capable of responding to and executinginstructions in a defined manner. Other examples include aspecial-purpose computer, a personal computer (“PC”), a workstation, aserver, a laptop, a cellular communications device, a Web-enabledtelephone, a personal digital assistant (“PDA”), a Web-enabled PDA, aninteractive television set, a settop box, a video tape recorder (“VTR”),a DVD player, an on-board (i.e., vehicle-mounted) computer, or any othercomponent, machine, tool, equipment, or some combination thereof capableof responding to and executing instructions.

An example of a controller, including an instant messaging controller,is a software application (e.g., operating system, browser application,micro browser application, server application, proxy application,gateway application, tunneling application, e-mail application; instantmessaging client, online service provider client application,interactive television client application, and/or Internet serviceprovider client) loaded on a device to command and direct communicationsenabled by the device. Other examples include a computer program, apiece of code, an applet, a Java applet, a script, an instruction,another device, or some combination thereof. for independently orcollectively instructing the device to interact and operate as desired.The controller may be embodied permanently or temporarily in any type ofmachine, component, physical or virtual equipment, storage medium, orpropagated signal capable of providing instructions to a device. Inparticular, the controller (e.g., software application, computerprogram) may be stored on a storage media or device (e.g., ROM, magneticdiskette, or propagated signal) readable by a general or special purposeprogrammable computer, such that if the storage media or device is readby a computer system, the functions described herein are performed.

Typically, a user is associated with an instant messaging onlineidentity. The instant messaging online identity may be maintained at aremote location by an instant messaging service provider. In oneimplementation, a user may subscribe to an instant messaging onlineidentity with a commercial instant messaging service provider, such asthose provided by America Online, Inc., Yahoo, Inc., Microsoft, Inc.,and other instant messaging service providers. In anotherimplementation, a user may be a part of an enterprise instant messagingservice and may have an instant messaging online identity as part of theenterprise system, such as a corporate instant messaging service. Insome cases, the instant messaging online identity may be part of both acommercially available instant message service provider and anenterprise instant message provider. In another implementation, the usermay have an instant messaging online identity in a point-to-point(“P2P”) instant messaging system.

The instant messaging online identity may be used to access one or morefeatures or services, for example, through submission of the onlineidentity and an associated password. The online identity may include aset of alphanumeric characters, symbols, tokens, or other types ofonline identities. In one implementation, a screen name may be used asthe online identity.

The instant messaging online identity typically is associated withinformation related to the user, such as a user's profile. The user'sprofile may include the user's preferences and a user-defined list ofother co-users or co-subscribers, which may be called a user's buddylist.

In general, a user's buddy list may be maintained with or accessible aspart of a user's profile and may be made accessible using a userinterface (VI) that provides the online status and capabilities ofcertain screen names, i.e., “buddies,” identified by the user. Inparticular, the instant message service provider may inform the userwhether or not identified buddies are online, i.e., currently accessingthe instant messaging service provider, enterprise host, or PTP node, asthe case may be. The instant message service provider also informs anyother user who has identified the user as a buddy that the user iscurrently online.

A buddy list may be used to facilitate instant messaging communicationsbetween users. For example, a user can activate an instant messaginguser interface that is pre-addressed to a buddy simply by selecting thescreen name of an online buddy from the buddy list.

Alternatively, by way of example, if a recipient is not a “buddy,” thefirst user generally initiates instant messaging communications byactivating a blank instant messaging conversation interface and thenaddressing that interface to the online identity (e.g., screen name) ofthe intended recipient. When necessary, a user may look up the screenname of an intended recipient using the intended recipient's e-mailaddress or other means.

For example, the participant list may include a “buddy list” that listsother co-users of one or more instant messaging systems. FIG. 2illustrates an exemplary buddy list 200. A buddy list interface 200 fora given user displays the screen names of user-defined co-users of aninstant messaging system with which the given user regularlycommunicates. The co-users form a buddy list for the given user.Communications with one of the co-users may be initiated throughselection of the corresponding identifier (e.g., screen name) for theco-user from the buddy list. The co-users may have been added to thebuddy list by the given user manually using identifiers of the co-usersin the instant messaging system that are known to the given user at thetime of addition.

The buddy list interface 200 includes a text box 20S that contains thebuddy list for the given user, who is identified by a screen name“AOLUser,” as indicated in the title bar 203 of the buddy list interface200. The buddy list in the buddy list interface 200 includes multiplescreen names 210 a-210 e. More particularly, the buddy list includes thescreen name “Friend1” 210 a, the screen name “Friend2” 210 b, the screenname “Mom” 210 c, the screen name “Dad” 210 d, and the screen name“Sister” 210 e.

The screen names within the buddy list shown by buddy list interface 200are organized into multiple buddy groups 2I5 a-215 c. Each screen namewithin the buddy list is associated with at least one of the buddygroups 2I5 a-215 c. The buddy list includes a “Buddies” buddy group21Sa, a “Family” buddy group 215 b, and an “Offline” buddy group 215 c.The screen name 210 a appears below the heading for the buddy group 215a because the screen name 210 a has been associated with the buddy group215 a and the corresponding user is present, that is, logged into theinstant messaging system and available to send and receive instantmessages. The heading for each of the buddy groups 215 a and 215 bindicates the number of buddies in the group currently logged into theinstant messaging system, as well as the total number of buddies in thegroup. For example, two out of the two members of the buddy group 215 aare logged into the instant messaging system for which the buddy listinterface 200 is displayed. Similarly, the heading for the “Offline”buddy group 2I5c indicates the number of other users on the buddy listthat are not logged into the system (i.e., 0) and the total number ofbuddies on the buddy list (i.e., 5). Typically, when users log into theinstant messaging system, screen names of the users are moved from the“Offline” buddy group 2I5 c to one of the other buddy groups 215 a or215 b.

The buddy list interface 200 also includes controls 220 that enable thegiven user to communicate with the co-users corresponding to the screennames 210 a-210 c. For example, the given user may send instantmessages, chat invitations, or e-mail messages to the communicationsidentities referenced in the buddy list through use of the controls 220.The controls 220 also enable the user to obtain information describingthe co-users, as well as to modify the set of co-users referenced in thebuddy list interface 200.

The buddy list interface 200 includes controls 225 that enable the givenuser to access other information not directly related to sending andreceiving instant messages. For example, the given user may use thecontrols to access e-mail messages or other special features of theinstant messaging system. The given user also may use the controls 225to modify preferences for the buddy list interface 200.

Different interfaces may be used to enable the transfer of instantmessaging sessions from a first instant messaging controller on onedevice to a second instant messaging controller on a second device. Theinterfaces enable the user to select a subset of the instant messagingsessions to transfer from among multiple instant messaging sessions.Referring to FIG. 3A, an instant messaging session transfer interface300 is illustrated. The instant messaging session transfer interface 300includes a listing of the current instant messaging sessions 305 a-305c. The current instant messaging sessions 305 a-305 c may be presentedwith corresponding metadata-type or bibliographic information such as,for example, the co-user's online identity or alias (e.g., screen name)307, the date the instant messaging session was opened 308, and the timethe instant messaging session started 309. Other metadata-type orbibliographic information also may be maintained and made perceivable tothe user to identify a particular instant messaging session. Othermetadata-type or bibliographic information may include the duration ofthe instant messaging session, the state of the co-user (e.g., active,idle, or away), and keywords from the session.

In the case where the user is only signed in to one other instantmessaging controller on one other device, when the user selects one ormore of the instant messaging sessions for transfer (step 105) theselected instant messaging sessions are transferred to the instantmessaging controller on that device (step 115). However, if the user issigned on to more than one other instant messaging controller on morethan one other device, a device selection box 310 is presented to theuser so the user can select which device or devices 315 a and 315 b totransfer the selected instant messaging sessions.

FIG. 3A illustrates an exemplary implementation of the user initiatingthe transfer of the instant messaging sessions from the instantmessaging controller on an incumbent device at which the listed instantmessaging sessions currently are made perceivable and from which thosesessions may be transferred responsive to user manipulation of theinterface. In this example, the user has selected to transfer theinstant messaging session 30Sb with Friend2. Since the user is signed onto multiple other devices, a device selection box 310 is presented tothe user to enable the user to select either or both of the devices 315a and 315 b to send the instant messaging session. For instance, theuser may be conducting the instant messaging session with Friend2 froman instant messaging controller on a desktop computer. If the user hasto walk away from the desktop computer but still wants to continue theinstant messaging session with Friend2 on the user's PDA (as opposed totheir laptop), then the user selects PDA 315 b from the device selectionbox 310. The selected instant messaging session 305 b is transferred tothe instant messaging controller on the PDA (step 115) and the instantmessaging session is made perceivable using the instant messagingcontroller on the PDA (step 120). When the instant messaging session istransferred, the instant messaging controller on the PDA receives theentire session history including some or all of the text of conversationbetween the user and Friend2. In one exemplary implementation, a newinstant messaging conversation interface is instantiated on the instantmessaging controller on the PDA and the conversation interface ispopulated with the transferred instant messaging session.

In one exemplary implementation, the user may designate a portion of thetext of the instant message that is to be transferred. For example, uponinitiating the transfer of an instant messaging session, the text of thesession may be presented to the user. The user may select all or aportion of the text to transfer by highlighting the desired using acursor control device. The designated text is then transferred to theinstant messaging controller on the later-invoked device.

FIG. 3B illustrates the exemplary implementation of the user initiatingthe transfer of the instant messaging sessions from the instantmessaging controller on the later-invoked device that is going toreceive the transferred instant messaging sessions from one or moreother instant messaging controllers on other devices. An instantmessaging session transfer interface 300 includes a listing of thecurrent instant messaging sessions 305 a-305 c identified by metadata orbibliographic-type information. The transfer interface 300 enables theuser to select one or more of the instant messaging sessions 305 a-305 cto receive. The transfer interface 300 also may include a deviceselection box 320 to enable the user to select the device 325 a or 325 bfrom which to receive the selected instant messaging session if thesession is mirrored at multiple other instant messaging controllers onmultiple other devices 325 a and 325 b.

Enabling the user to select the device 325 a or 325 b from which toreceive the selected instant messaging session may be advantageous, forexample, if one of the devices 325 a or 325 b has a more completeinstant messaging session than the other device. For instance, laptop325 b may only have a partial instant messaging session 30Sb because theinstant messaging controller on the laptop 325 b was launched after theinstant messaging session had begun on the instant messaging controlleron the desktop 325 a. In one exemplary implementation, the device withthe most complete instant messaging session may be distinguished fromother devices using a visual identifier. Additionally or alternatively,the device with the most complete instant messaging session may beauto-selected for use in the transfer.

Enabling the user to initiate the transfer of a subset of instantmessaging sessions from among multiple instant messaging sessions fromthe receiving instant messaging controller on the later-invoked deviceis advantageous, for example, in the event the user walks away from thedevice where the instant messaging session was taking place. Forexample, if the user was conducting an instant messaging session withFriend2 305 b from his desktop computer 325 a and the user walked awayfrom the desktop computer 325 a before transferring the instantmessaging session to his PDA, then the user could still initiate thetransfer of the session from the PDA to enable continued participationin or review of the conversation from the user's PDA

FIG. 3C illustrates an exemplary implementation of the user initiatingthe transfer of more that one or all of the current instant messagingsessions. An instant messaging transfer interface 300 includes a listingof the current instant messaging sessions 305 a-305 c identified bymetadata or bibliographic-type information. In this example, the userhas selected all three of the current instant messaging sessions 305a-30Sc for transfer concurrently. The selection may be made using acursor control device (e.g., a mouse) selection or manipulation or usingradio button or checkbox selection (not shown). The transfer interface300 also may include a device selection box 320 to enable the user toselect the device 325 a or 325 b from which to receive the selectedinstant messaging session if the session is mirrored at multiple otherinstant messaging controllers on multiple other devices 325 a and 325 b.

The instant messaging transfer interfaces described above with respectto FIGS. 3A-3C may be triggered or invoked in different ways. Forexample, the transfer interfaces may be invoked manually by an input oran action of the user. For instance, the transfer interfaces may beinvoked manually using a menu option on a toolbar within the instantmessaging controller or by a right-click of a cursor control device thatinvokes a drop-down menu with an option to instantiate the transferinterface. In another exemplary implementation, the transfer interfacesmay be invoked automatically based on a determined event, such as theuser signing on to an instant messaging controller at another device forFIG. 3A or the device at which the transfer interface appears for FIGS.3B and 3C.

In another exemplary implementation, an instant messaging session may betransferred from one instant messaging controller on one device toanother instant messaging controller on another device using an instantmessaging conversation interface. FIG. 4A illustrates an instantmessaging conversation interface 400 that is used to conduct an instantmessaging session. The instant messaging conversation interface 400includes a “From” portion 405 that lists the user who initiated theinstant messaging session, a “To” portion 410 that lists the co-userwith whom the user is exchanging instant messages, and an instantmessaging conversation portion 415 that displays a chronological log ofthe instant messages exchanged between the user and co-user. Theinterface 400 also includes an instant messaging session transferportion 420. The instant messaging session transfer portion 420 isconfigured to enable the user to select one or more devices with whichto transfer some or all of the instant messaging session represented bythe instant messaging conversation interface 400, which includes thetransfer of the chronological log of instant messages exchanged betweenthe user and the co-user. In one implementation, the instant messagingsession transfer portion 420 includes a drop-down menu 425 that, whenselected, reveals a scrollable window 430 that lists the devices 435 aand 435 b to which the instant messaging session can be transferred. Inthis example, the user is logged on to two other instant messagingcontrollers, one on a laptop 435 a and one on a PDA 435 b. If the userhad been logged on to only one other device, the drop-down menu 425 andthe scrollable window 430 may list just that one device or they may notlist any devices at all and the instant messaging session may betransferred to the one device upon selection of the instant messagingtransfer portion 420.

In another exemplary implementation, an instant messaging transferportion and a drop-down menu in an instant messaging conversationinterface may be used to select an instant messaging session to receiveor pull into the conversation interface, where the instant messagingsession currently resides only on other instant messaging controllers onother devices. The instant messaging transfer portion may appear only ifthe instant messaging session is available at the other instantmessaging controller for transfer.

Referring to FIG. 4B, an instant messaging conversation interface 400includes a “From” portion 405 that lists the user who initiated theinstant messaging session, a “To” portion 410 that lists the co-userwith whom the user is exchanging instant messages, and an instantmessaging conversation portion 415 that displays a chronological log ofthe instant messages exchanged between the user and co-user. Theinterface 400 also includes an instant messaging session transferportion 420. The instant messaging session transfer portion 420 isconfigured to enable the user to select one or more devices from whichto receive some or all of an instant messaging session into theconversation interface 400, which includes receiving the chronologicallog of instant messages exchanged between the user and the co-user. Thereceived instant messaging session is populated in the instant messagingconversation portion 415. The transfer portion 420 may only be enabledand/or made perceivable if the instant messaging session is available atthe other instant messaging controller for transfer. In this example,the user is logged on to two other instant messaging controllers, one ona laptop 435 a and one on a PDA 435 b. If the user had been logged on toonly one other device, the drop-down menu 425 and the scrollable window430 may list just that one device or they may not list any devices atall, and the instant messaging session may be received from the onedevice upon selection of the instant messaging transfer portion 420.

In one exemplary implementation, the user may designate preferences asto which instant messaging sessions are “mirrored.” For instance, whenan instance messaging session has been transferred to another instantmessaging controller on another device, the text of the continuedinstant message exchange between the user and the co-user may beperceivable on both the device that sent the instant messaging sessionand the device that transferred the instant messaging session. However,the user may not desire to have the conversation continue to be madeperceivable on the incumbent device. Either prior to or after thetransfer of the instant messaging session the user may be presented withan interface that requests whether the user wants to continue themirrored conversation on the incumbent device. Referring to FIG. 5A, aninterface 500 is displayed which requests whether the user wants to havethe instant messaging session continue on the device from which theinstant messaging session is being transferred. If the user selects the“Yes” button 505, then the instant messaging session continues to bemade perceivable on the device that sent the instant messaging session.If the user selects the “No” button 510, then the instant messagingsession is no longer made perceivable on the device that sent theinstant messaging session.

In one exemplary implementation, when an ongoing instant messagingsession is made perceivable on more than one instant messagingcontroller on more than one device, the instant messaging session may nolonger be made perceivable if the state of the instant messagingcontroller and/or the device is idle or away. An idle state is when theuser has not been active on the instant messaging controller or thedevice for a configurable period of time. An away state is when the usermanually sets the instant messaging controller in a non-active state.The user may set preferences regarding whether to continue mirroringtransferred instant messaging sessions during an idle and/or an awaystate. Referring to FIG. 5B, an interface 550 is displayed to solicitfeedback to indicate whether the user wants to continue viewing theinstant messaging session after an idle or an away state. If the userselects the “Yes” button 555, then the instant messaging sessioncontinues to be made perceivable on the device even when the instantmessaging controller and/or the device is in an idle or an away state.If the user selects the “No” button 560, the instant messaging sessionceases being perceivable when the instant messaging controller and/orthe device is in an idle or an away state. Thus, the instant messagingsession may continue to be mirrored and perceivable on the device untilthey are interrupted by an idle or an away state at which time theinstant messaging session is no longer made perceivable.

In another exemplary implementation, the user may configure globalsettings specify on a session-by-session basis that apply to more thanone session. For example, the user may specify a global setting that alltransferred instant messaging sessions are to be copied or converselythat all transferred instant messaging sessions are to be transitionedand, therefore, not copied. Moreover, a user may want to set up globalpreferences on a device-by-device basis such that, for example,transfers to a PDA default to transition while transfers from PDA merelycopy.

Referring to FIG. 6A, an exemplary timeline is illustrated for therefreshing of an instant messaging session when returning from an idlestate. The timeline includes an event column 600, a desktop userinterface column 605 and a PDA user interface column 610. The firstevent is when the online identity, AOL User, is logged onto an instantmessaging controller on a desktop computing device and begins andinstant messaging session with co-user, Friend2 (600 a). The userinterface on the desktop (605 a) displays an instant messagingconversation interface with a disabled transfer session button. Thetransfer session button is disable because AOL User is only signed on toone instant messaging controller and there are no other instantmessaging controllers available to transfer the instant messagingsession. The instant messaging conversation interface portion displaysthe text of the instant messaging session.

Next, AOL User invokes the instant messaging controller on the PDA (600b). The instant messaging conversation interface (605 b) now display anenabled transfer session button because another instant messagingcontroller is available to transfer the instant messaging session withFriend2. The conversation interface portion continues to display theongoing conversation of the instant messaging session. The PDA displaysan instant messaging session transfer interface 61˜b, which lists theinstant messaging session with Friend2 as available for transfer to thePDA. In one exemplary implementation, the desktop (605) may display aninstant messaging session transfer interface (not shown) that enablesAOL User to transfer this instant messaging session with Friend2 as wellas other instant messaging sessions with other co-users. The usertransfers the instant messaging session to the PDA so that the instantmessaging session is mirrored on both the desktop and the PDA.

When AOL User is idle at the desktop but active at the PDA for athreshold period of time (600 c), the interface on the desktop (605 c)indicates that the instant messaging session is blocked due to an idlestate and in the instant messaging conversation interface (610 c) on thePDA the instant messaging session conversation continues. In oneexemplary implementation, the ongoing instant messaging session will nottrigger or transition the desktop from the idle state to an activestate. For instance, a host system setting may redirect messages fromFriend2 only to the PDA once the desktop is in an idle state.

When AOL User returns to the desktop and the desktop is in an activestate (600 d), then the instant messaging conversation interface (605 d)may be refreshed so that the entire conversation is perceivable on thedesktop. In one exemplary implementation, when the instant messagingcontroller and/or the device returns to an active state, the instantmessaging sessions may be refreshed automatically. In another exemplaryimplementation, the user may designate which of the one or moreinterrupted instant messaging sessions to refresh. Referring to FIG. 6B,an exemplary selection interface 675 illustrates one or more instantmessaging sessions that the user may select on an individual or on acollective basis to refresh.

In yet another exemplary implementation, when an instant messagingsession is transferred back to a device, the legacy instant messagingconversation interface may be refreshed with the entire instantmessaging session or the legacy instant messaging conversation interfacemay be closed and a new instant messaging conversation interfaceinstantiated and populated with the transferred back instant messagingwindow.

In one exemplary implementation, user-inspired messages may be madeperceivable on all instant messaging controllers on all devices. Thisensures that the user is able to view an entire instant messagingconversation of user-inspired messages and co-user messages on all ofthe instant messaging controllers and not just on the instant messagingcontroller from which the user is composing and sending theuser-inspired messages.

FIGS. 7 and 8 illustrate an exemplary block diagram 700 and 800 of acommunications system that may be used as part of the implementation ofthe features described above.

For illustrative purposes, FIGS. 7 and 8 show an example of acommunications system for implementing techniques for transferringelectronic data, including instant messages. For brevity, severalelements in the figures described below are represented as monolithicentities. However, as would be understood by one skilled in the art,these elements each may include numerous interconnected computers andcomponents designed to perform a set of specified operations and/or maybe dedicated to a particular geographical region.

Referring to FIG. 7, a communications system 700 is capable ofdelivering and exchanging data between a user system 705 and a providersystem 710 through a communications link 715. The user system 705 mayinclude a client system and the provider system 710 may include a hostsystem. The user system 705 typically includes one or more user devices720 and/or user controllers 725, and the provider system 710 typicallyincludes one or more provider devices 735 and/or provider controllers740. For example, the user system 705 or the provider system 710 mayinclude one or more general-purpose computers (e.g., personalcomputers), one or more special-purpose computers (e.g., devicesspecifically programmed to communicate with each other and/or the usersystem 705 or the provider system 710), or a combination of one or moregeneral-purpose computers and one or more special-purpose computers. Theuser system 705 and the provider system 710 may be arranged to operatewithin or in concert with one or more other systems, such as, forexample, one or more Local Area Networks (“LANs”) and/or one or moreWide Area Networks (“WANs”).

The provider system 710 may include a communication interface such as anelectronic mail gateway. For instance, the provider system 710 mayinclude a dedicated mailing system that is implemented by specializedhardware or executed by a general purpose processor capable of runningvarious applications, such as electronic mailer programs, and capable ofemploying various file transfer protocols, such as the Simple MailTransfer Protocol (“SMTP”). The communications interface of providersystem 710 enables communications between the provider system 710 andother systems through, for example, communications link 715.

The user device 720 (or the provider device 735) is generally capable ofexecuting instructions under the command of a user controller 725 (or aprovider controller 740). The user device 720 (or the provider device735) is connected to the user controller 725 (or the provider controller740) by a wired or wireless data pathway 730 or 745 capable ofdelivering data.

The user device 720, the user controller 725, the provider device 735,and the provider controller 740 each typically include one or morehardware components and/or software components. An example of a userdevice 720 or a provider device 735 is a general-purpose computer (e.g.,a personal computer) capable of responding to and executing instructionsin a defined manner. Other examples include a special-purpose computer,a workstation, a server, a device, a component, other physical orvirtual equipment or some combination thereof capable of responding toand executing instructions. The user device 720 and the provider device735 may include devices that are capable of peer-to-peer communications.

An example of a user controller 725 or a provider controller 740 is asoftware application loaded on the user device no or the provider device735 for commanding and directing communications enabled by the userdevice no or the provider device 735. Other examples include a program,a piece of code, an instruction, a device, a computer, a computersystem, or a combination thereof, for independently or collectivelyinstructing the user device 720 or the provider device 735 to interactand operate as described. The user controller 725 and the providercontroller 740 may be embodied permanently or temporarily in any type ofmachine, component, physical or virtual equipment, storage medium, orpropagated signal capable of providing instructions to the user device720 or the provider device 735.

The communications link 715 typically includes a delivery network 760making a direct or indirect communication between the user system 705and the provider system 710, irrespective of physical separation.Examples of a delivery network 760 include the Internet, the World WideWeb, WANs, LANs, analog or digital wired and wireless telephone networks(e.g., PSTN, ISDN, and xDSL), radio, television, cable, satellite,and/or any other delivery mechanism for carrying data. Thecommunications link 715 may include communication pathways 750 and 755that enable communications through the one or more delivery networks 760described above. Each of the communication pathways 750 and 755 mayinclude, for example, a wired, wireless, cable or satellitecommunication pathway.

An electronic information store 780 may be connected to the providersystem 710, included as a component of the provider system 710, and/orconnected to the delivery network 760. The electronic information store780 may be a repository for electronic information that may be in anindexed and/or searchable format. For example, in one implementation,the electronic information store 780 may be used to store informationrelated to instant messaging online identities. In another exemplaryimplementation, electronic information store 780 may be used to recordand to store instant messaging history sessions.

FIG. 8 illustrates a communications system 800 including a user system805 communicating with a provider system 810 through a communicationslink 815. User system 805 typically includes one or more user devices820 and one or more user controllers 825 for controlling the userdevices 820. Provider system 810 typically includes one or more providerdevices 835 and one or more provider controllers 840 for controlling theprovider devices 835. The communications link 815 may includecommunication pathways 850 and 855 that enable communications throughthe one or more delivery networks 860.

Examples of each element within the communications system of FIG. 8 arebroadly described above with respect to FIG. 7. In particular, theprovider system 810 and communications link 815 typically haveattributes comparable to those described with respect to the providersystem 710 and the communications link 715 of FIG. 7. Likewise, the usersystem 805 of FIG. 8 typically has attributes comparable to andillustrates one possible implementation of the user system 705 of FIG.7.

The user device 820 typically includes a general-purpose computer 870having an internal or external storage 872 for storing data and programssuch as an operating system 874 (e.g., DOS, Windows™, Windows 95™,Windows98™, Windows 2000™, Windows Me™, Windows XP™, Windows NT™, OS/2,or Linux) and one or more application programs. Examples of applicationprograms include authoring applications 876 (e.g., word processingprograms, database programs, spreadsheet programs, or graphics programs)capable of generating documents or other electronic content; clientapplications 878 (e.g., stand alone e-mail client or AOL client,CompuServe client, AIM client, AOL TV client, or ISP client, all ofwhich may include a built-in or embedded e-mail or instant messagingclient) capable of communicating with other computer users, accessingvarious computer resources, and viewing, creating, or otherwisemanipulating electronic content; and browser applications 880 (e.g.,Netscape's Navigator or Microsoft's Internet Explorer) capable ofrendering standard Internet content and also capable of supporting aweb-based e-mail client and a web-based instant messaging client.

The general-purpose computer 870 also includes a central processing unit882 (CPU) for executing instructions in response to commands from theuser controller 825. In one implementation, the user controller 825includes one or more of the application programs installed on theinternal or external storage 872 of the general-purpose computer 870. Inanother implementation, the user controller 825 includes applicationprograms stored in and performed by one or more device(s) external tothe general-purpose computer 870.

The general-purpose computer also includes a communication device 884for sending and receiving data. One example of the communication device884 is a modem. Other examples include a transceiver, a set-top box, acommunication card, a satellite dish, an antenna, or another networkadapter capable of transmitting and receiving data over thecommunications link 815 through a wired or wireless data pathway 850.The general-purpose computer 870 also may include a TV tuner 886 forreceiving television programming in the form of broadcast, satellite,and/or cable TV signals. As a result, the user device 820 canselectively and/or simultaneously display network content received bycommunications device 884 and television programming content received bythe TV tuner 886.

The general-purpose computer 870 typically includes an input/outputinterface 888 for wired or wireless connection to various peripheraldevices 890. Examples of peripheral devices 890 include, but are notlimited to, a mouse 891, a mobile phone 892, a personal digitalassistant 893 (PDA). a MP3 player (not shown), a keyboard 894, a displaymonitor 895 with or without a touch screen input, a TV remote control896 for receiving information from and rendering information tosubscribers, and an audiovisual input device 898.

Although FIG. 8 illustrates devices such as a mobile telephone 892, aPDA 893, and a TV remote control 896 as being peripheral with respect tothe general-purpose computer 870, in another implementation, suchdevices may themselves include the functionality of the general-purposecomputer 870 and operate as the user device 820. For example, the mobilephone 892 or the PDA 893 may include computing and networkingcapabilities and function as a user device 820 by accessing the deliverynetwork 860 and communicating with the provider system 810. Furthermore,the user system 805 may include one, some or all of the components anddevices described above.

The described systems, methods, and techniques may be implemented indigital electronic circuitry, computer hardware, firmware, software, orin combinations of these elements. Apparatus embodying these techniquesmay include appropriate input and output devices, a computer processor,and a computer program product tangibly embodied in a machine-readablestorage device for execution by a programmable processor. A processembodying these techniques may be performed by a programmable processorexecuting a program of instructions to perform desired functions byoperating on input data and generating appropriate output. Thetechniques may be implemented in one or more computer programs that areexecutable on a programmable system including at least one programmableprocessor coupled to receive data and instructions from, and to transmitdata and instructions to, a data storage system, at least one inputdevice, and at least one output device. Each computer program may beimplemented in a high-level procedural or object-oriented programminglanguage, or in assembly or machine language if desired; and in anycase, the language may be a compiled or interpreted language. Suitableprocessors include, by way of example, both general and special purposemicroprocessors. Generally, a processor will receive instructions anddata from a read-only memory and/or a random access memory. Storagedevices suitable for tangibly embodying computer program instructionsand data include all forms of non-volatile memory, including by way ofexample semiconductor memory devices, such as Erasable ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM), and flash memory devices; magnetic disks such asinternal hard disks and removable disks; magneto-optical disks; andCompact Disc Read-Only Memory (CD-ROM). Any of the foregoing may besupplemented by, or incorporated in, specially-designed ASICs(application-specific integrated circuits).

Techniques described may find particular utility when applied or adaptedto systems and processes that maintain some or all status information orhistory locally as they enable sharing of local content among deviceswithout complete reliance on centralized storage or functionality.

It will be understood that various modifications may be made withoutdeparting from the spirit and scope of the claims. For example,advantageous results still could be achieved if steps of the disclosedtechniques were performed in a different order and/or if components inthe disclosed systems were combined in a different manner and/orreplaced or supplemented by other components. Accordingly, otherimplementations are within the scope of the following claims. Thesegeneral and specific aspects may be implemented using a system. amethod, or a computer program, or any combination of systems, methods,and computer programs.

1.-20. (canceled)
 21. A non-transitory computer-readable medium storinginstructions executable by one or more processors, the instructions whenexecuted by the one or more processors causing the one or moreprocessors to perform operations comprising: cause a device selectionbox to be displayed so that a user can select one or more devices fortransfer of an instant messaging session; receive a selection totransfer the instant messaging session from a first instant messagingcontroller to a second instant messaging controller; transfer at least aportion of the instant messaging session from the first instantmessaging controller to the second instant messaging controller; makethe transferred portion of the instant messaging session perceivable onthe second instant messaging controller; and after making thetransferred portion perceivable, make user-inspired instant messagesperceivable on both the first instant messaging controller and thesecond instant messaging controller such that the user is able to viewthe user-inspired instant messages and co-user messages for the instantmessaging session on the first instant messaging controller and thesecond instant messaging controller.
 22. The computer-readable medium ofclaim 21, wherein the user-inspired instant messages are madeperceivable on both the first instant messaging controller and thesecond instant messaging controller based on a stored user preference.23. A method to transfer instant messaging sessions, the methodcomprising: receiving a selection to transfer an instant messagingsession from a first instant messaging controller to a second instantmessaging controller; transferring at least a portion of the instantmessaging session from the first instant messaging controller to thesecond instant messaging controller; making the transferred portion ofthe instant messaging session perceivable on the second instantmessaging controller; and after making the transferred portionperceivable, making user-inspired instant messages perceivable on boththe first instant messaging controller and the second instant messagingcontroller such that a user is able to view the user-inspired instantmessages and co-user messages for the instant messaging session on thefirst instant messaging controller and the second instant messagingcontroller.
 24. The method of claim 23, further comprising: ceasingmaking the user-inspired instant messages perceivable if a state of oneof the instant messaging controllers is an idle state or an away state.25. The method of claim 24, further comprising refreshing the instantmessaging session upon the one of the instant messaging controllerstransitioning into an active state.
 26. The method of claim 23, furthercomprising: when the user is signed on to more than one other instantmessaging controllers on more than one other device, allowing the userto select which device or devices to transfer the instant messagingsession.
 27. The method of claim 26, further comprising, displaying adevice selection box, wherein the device selection box enables the userto select which device or devices to transfer the instant messagingsession.
 28. The method of claim 27, wherein the device selection boxincludes a list of instant messaging controllers that the user is signedon to.
 29. The method of claim 23, further comprising: allowing the userto select the instant messaging session to transfer from a plurality ofinstant messaging sessions.
 30. The method of claim 23, wherein theuser-inspired instant messages are made perceivable on both the firstinstant messaging controller and the second instant messaging controllerbased on a user preference.
 31. The method of claim 30, furthercomprising: receiving the user preference about whether to makeuser-inspired instant messages perceivable on more than one instantmessaging controller; and storing the user preference.
 32. A system totransfer instant messaging sessions, comprising: one or more processors;a data store comprising instructions executable by the one or moreprocessors, the instructions when executed by the one or more processorscausing the one or more processors to perform operations, comprising:receive a selection to transfer an instant messaging session from afirst instant messaging controller to a second instant messagingcontroller; transfer at least a portion of the instant messaging sessionfrom the first instant messaging controller to the second instantmessaging controller; make the transferred portion of the instantmessaging session perceivable on the second instant messagingcontroller; and after making the transferred portion perceivable, makeuser-inspired instant messages perceivable on both the first instantmessaging controller and the second instant messaging controller suchthat a user is able to view the user-inspired instant messages andco-user messages for the instant messaging session on the first instantmessaging controller and the second instant messaging controller. 33.The system of claim 32, wherein the instructions when executed by theone or more processors further cause the one or more processors toperform operations, comprising: cease making the user-inspired instantmessages perceivable if a state of one of the instant messagingcontrollers is an idle state or an away state.
 34. The system of claim33, wherein the instructions when executed by the one or more processorsfurther cause the one or more processors to perform operations,comprising: refresh the instant messaging session upon the one of theinstant messaging controllers transitioning into an active state. 35.The system of claim 33, wherein the instructions when executed by theone or more processors further cause the one or more processors toperform operations, comprising: when the user is signed on to more thanone other instant messaging controller on more than one other device,allow the user to select which device or devices to transfer the instantmessaging session.
 36. The system of claim 35, wherein the instructionswhen executed by the one or more processors further cause the one ormore processors to perform operations, comprising: cause a deviceselection box to be displayed so the user can select which device ordevices to transfer the instant messaging session.
 37. The system ofclaim 36, wherein the device selection box includes a list of instantmessaging controllers that the user is signed on to.
 38. The system ofclaim 32, wherein the instructions when executed by the one or moreprocessors further cause the one or more processors to performoperations, comprising: allow the user to select the instant messagingsession to transfer from a plurality of instant messaging sessions. 39.The system of claim 32, wherein the instructions to make user-inspiredinstant messages perceivable on both the first instant messagingcontroller and the second instant messaging controller further compriseinstructions to make the user-inspired instant messages perceivable onboth the first instant messaging controller and the second instantmessaging controller based on a user preference.
 40. The system of claim39, wherein the instructions when executed by the one or more processorsfurther cause the one or more processors to perform operations,comprising: receive the user preference about whether to makeuser-inspired instant messages perceivable on more than one instantmessaging controller; and store the user preference.